Method and terminal for receiving pdsch

ABSTRACT

This disclosure provides a method for receiving a PDSCH and a terminal thereof. The method for receiving a PDSCH includes: after occurrence of a beam failure event is determined, monitoring a PDCCH on a CORESET-BFR and a PDCCH on another CORESET, determining a QCL parameter of the PDSCH based on a QCL parameter of the PDCCH on the CORESET-BFR, a QCL parameter of the PDCCH on the another CORESET, a QCL parameter of a PDCCH on a CORESET that contains DCI scheduling the PDSCH, or a QCL parameter indicated by TCI state information in the DCI scheduling the PDSCH, and receiving the PDSCH based on the determined QCL parameter.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a bypass continuation of PCT Application No.PCT/CN2019/077791 filed Mar. 12, 2019, which claims priority to ChinesePatent Application No. 201810272571.9, filed in China on Mar. 29, 2018,both of which are incorporated herein by reference in their entireties.

TECHNICAL FIELD

Embodiments of this disclosure relate to the field of wirelesscommunications technologies, and in particular, to a method forreceiving a Physical Downlink Shared Channel (PDSCH) and a terminalthereof.

BACKGROUND

With development of communications technologies, communicationefficiency has received increasing attention. The following introduces afew technical terms.

1. Multi-Antenna

Standards for radio access technologies such as Long Term Evolution(LTE)/LTE-advanced (LTE-A) are built based on technologies ofMultiple-Input Multiple-Output (MIMO) and Orthogonal Frequency DivisionMultiplexing (OFDM). The MIMO technology takes advantage of a spatialdegree of freedom brought by a multi-antenna system to improve a peakrate and a system spectrum utilization.

It can be foreseen that in the future 5G mobile communications system,the massive MIMO technology with more antenna ports will be introduced.The massive MIMO technology uses a larger quantity of antenna arrays,and can greatly improve system frequency band utilization efficiency andsupport a larger quantity of access users.

2. High Frequency Band

In studies on a next-generation communications system later than 4G, anoperating frequency band above 6 GHz or even up to a maximum of about100 GHz is supported by the system. The high frequency band hasrelatively abundant free frequency resources and can provide a higherthroughput for data transmission. At present, the 3GPP has completed thework of modeling for high frequency channels. High frequency signalshave shorter wavelengths. Compared with a low frequency band, the highfrequency band allows deployment of more antenna arrays on a panel ofthe same size and uses a beamforming technology to form a beam withbetter directivity and narrower wave lobes. Therefore, a combination ofmassive antennas and high frequency communication is one of the futuretrends.

3. Beam Failure Recovery Mechanism

In the high frequency band communications system, cases such as possibleblocking of signal propagation due to a relatively short wavelength of aradio signal cause interrupted signal propagation. Use of radio linkrebuilding in the prior art is time-consuming, and therefore, the beamfailure recovery mechanism is introduced. The mechanism includes thefollowing four steps:

(1) A terminal determines occurrence of a beam failure event.

(2) The terminal selects a candidate beam.

(3) The terminal sends a beam failure recovery request.

(4) The terminal monitors a control resource set used for beam failurerecovery (Control Resource Set Beam Failure Recovery, CORESET-BFR)configured for the terminal by a network device, and receives adedicated Physical Downlink Control Channel (PDCCH), so as to receiveresponse information from the network device in response to the beamfailure recovery request.

When the terminal receives a PDSCH during beam failure recovery, theterminal assumes that a PDSCH DMRS (demodulation reference signal) portand the monitored PDCCH are quasi co-located (Quasi-colocation, QCL).

Whether to monitor another network-configured Control-Resource Set(CORESET) before a beam failure when a response in the PDCCH on theCORESET-BFR is monitored during beam failure recovery is not describedin the prior art. When the two CORESETs need to be monitored, there isno solution to determining a QCL parameter of the PDSCH to enable theterminal to correctly receive the PDSCH.

SUMMARY

Embodiments of this disclosure provide a method for receiving a PDSCHand a terminal thereof, so as to resolve an issue of how to correctlyreceive a PDSCH during beam failure recovery.

To resolve the foregoing issue, this disclosure is implemented asfollows:

According to a first aspect, an embodiment of this disclosure provides amethod, for receiving a PDSCH, applied to a terminal and including:

after occurrence of a beam failure event is determined, monitoring aPDCCH on a CORESET-BFR and a PDCCH on another CORESET, where theCORESET-BFR and the another CORESET are configured for the terminal by anetwork device; and

determining a QCL parameter of the PDSCH based on a QCL parameter of thePDCCH on the CORESET-BFR, a QCL parameter of the PDCCH on the anotherCORESET, a QCL parameter of a PDCCH on a CORESET that contains DownlinkControl Information (DCI) scheduling the PDSCH, or a QCL parameterindicated by Transmission Configuration Indication (TCI) stateinformation in the DCI scheduling the PDSCH, and receiving the PDSCHbased on the determined QCL parameter.

According to a second aspect, an embodiment of this disclosure providesa terminal, including:

a monitoring module, configured to, after occurrence of a beam failureevent is determined, monitor a PDCCH on a CORESET-BFR and a PDCCH onanother CORESET, where the CORESET-BFR and the another CORESET areconfigured for the terminal by a network device;

a determining module, configured to determine a QCL parameter of a PDSCHbased on a QCL parameter of the PDCCH on the CORESET-BFR, a QCLparameter of the PDCCH on the another CORESET, a QCL parameter of aPDCCH on a CORESET that contains DCI scheduling the PDSCH, or a QCLparameter indicated by TCI state information in the DCI scheduling thePDSCH; and

a receiving module, configured to receive the PDSCH based on thedetermined QCL parameter.

According to a third aspect, an embodiment of this disclosure provides aterminal, including a processor, a memory, and a program that is storedin the memory and capable of running on the processor. When the programis executed by the processor, the steps of the foregoing method forreceiving a PDSCH are implemented.

According to a fourth aspect, an embodiment of this disclosure providesa computer-readable storage medium, the computer-readable storage mediumstoring a program, where when the program is executed by a processor,the steps of the foregoing method for receiving a PDSCH are implemented.

In the embodiments of this disclosure, the QCL parameter of the PDSCHcan be determined during beam failure recovery, so that the PDSCH iscorrectly received.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic flowchart of a method for receiving a PDSCHaccording to an embodiment of this disclosure;

FIG. 2 is a schematic structural diagram of a terminal according to anembodiment of this disclosure; and

FIG. 3 is a schematic structural diagram of a terminal according toanother embodiment of this disclosure.

DETAILED DESCRIPTION

The following clearly describes the technical solutions in theembodiments of this disclosure with reference to the accompanyingdrawings in the embodiments of this disclosure. Apparently, thedescribed embodiments are some rather than all of the embodiments ofthis disclosure. Based on the embodiments of this disclosure, all otherembodiments derived by persons of ordinary skill in the art withoutcreative efforts fall within the protection scope of this disclosure.

Referring to FIG. 1, an embodiment of this disclosure provides a methodfor receiving a PDSCH, applied to a terminal and including:

Step 101: After occurrence of a beam failure event is determined,monitor a PDCCH on a CORESET-BFR and a PDCCH on another CORESET, wherethe CORESET-BFR and the another CORESET are configured for the terminalby a network device.

Step 102: Determine a QCL parameter of the PDSCH based on a QCLparameter of the PDCCH on the CORESET-BFR, a QCL parameter of the PDCCHon the another CORESET, a QCL parameter of a PDCCH on a CORESET that DCIscheduling the PDSCH, or a QCL parameter indicated by TCI stateinformation in the DCI scheduling the PDSCH, and receive the PDSCH basedon the determined QCL parameter.

The another CORESET is a CORESET other than the COREET-BFR that isconfigured for the terminal by the network device.

In this embodiment of this disclosure, the QCL parameter of the PDSCHcan be determined during beam failure recovery, so that the PDSCH iscorrectly received.

In this embodiment of this disclosure, before the step of determining aQCL parameter of the PDSCH, the method further includes:

receiving configuration information, sent by the network device, of theCORESET-BFR and the another CORESET, where the configuration informationincludes TCI state information used to indicate the QCL parameter of thePDCCH on the CORESET-BFR and TCI state information used to indicate theQCL parameter of the PDCCH on the another CORESET.

The CORESET-BFR is configured to monitor a gNB response on a dedicatedPDCCH during beam failure recovery. The response is response informationfed back by the network device (which is the gNB) in response to a beamfailure recovery request sent by the terminal. The beam failure recoveryrequest is sent to the network device after occurrence of the beamfailure event is determined, which is described in detail in thefollowing content.

The another CORESET is configured to transmit a PDCCH during normalcommunication. Before the terminal determines occurrence of the beamfailure event, the terminal monitors the another CORESET other than theCORESET-BFR configured by the network device, so as to receive thePDCCH.

In this embodiment of this disclosure, the QCL parameter of the PDCCH onthe another CORESET and the QCL parameter of the PDCCH on theCORESET-BFR are the same or different.

In this embodiment of this disclosure, the network device sends theconfiguration information of the CORESET-BFR and the another CORESET tothe terminal by using higher-layer signaling.

In the related technology, the network device configures acorrespondence between a TCI state and a Reference Signal (RS) for theterminal by using Radio Resource Control (RRC) signaling.

When the TCI is used for QCL indication for a PDCCH, the network deviceconfigures K (K is an integer greater than or equal to 1) TCI states foreach CORESET. When K>1, MAC CE indicates one TCI state. When K=1, noadditional MAC CE signaling is required. When the terminal monitors thePDCCH on the CORESET, the same QCL (i.e., the same TCI state) is usedfor PDCCHs of all search spaces (search space) within the CORESET.

RRC signaling or RRC+MAC CE is used to notify one TCI state, and an RSresource (such as a periodic CSI-RS resource, a semi-persistent CSI-RSresource, or an SS block) in an RS set corresponding to the TCI stateand a UE (user equipment or user device)-specific PDCCH DMRS(demodulation reference signal) port are spatial QCL. UE can determine,based on the TCI state, to use which receive beam for receiving thePDCCH.

When the TCI is used for QCL indication for a PDSCH, the network deviceactivates 2^(N) (N is a positive integer greater than or equal to 1) TCIstates and notifies the TCI states by using an N-bit TCI field in DCI.An RS resource in an RS set corresponding to the TCI states and a DMRSport of the PDSCH to be scheduled are QCL. The terminal can determine,based on the TCI states, to use which receive beam for receiving thePDSCH. In two cases in which the DCI contains or does not contain theTCI field, when a scheduling offset is less than or equal to k (thescheduling offset is a time interval between a time of receiving the DCIand a time of receiving a PDSCH scheduled by the DCI), k is a presetthreshold, and a default TCI state is used for the QCL of the PDSCH. Thedefault TCI state is a control channel QCL indication, and the controlchannel QCL indication is determined by a TCI state of a CORESET with asmallest ID in a slot in which a control channel exists.

For initial TCI states of a PDCCH and a PDSCH, between initial RRCconfiguration and activation of the TCI states by using the MAC CE, aPDCCH DMRS and a PDSCH DMRS are spatial QCL with a SynchronizationSignal Block (SSB) that is determined upon initial access.

The following describes a beam failure recovery process in detail.

In this embodiment of this disclosure, the terminal first performs beamfailure detection. Specifically, the terminal measures a Beam FailureDetection Reference Signal (BFD RS) at a physical layer and determineswhether a beam failure event occurs based on a measurement result. Adetermining criterion is as follows: If it is detected that metrics(hypothetical PDCCH BLER) of all serving control beams meet a presetcondition (e.g., exceeding a preset threshold), one beam failureinstance is determined. The physical layer of the terminal reports anindication to a higher layer (e.g., a MAC layer) of the terminal. Thereporting is made periodically. However, if it is determined that nobeam failure instance occurs, no indication is reported to the higherlayer. The higher layer of the terminal uses a counter to count theindications reported by the physical layer. When a maximum countconfigured by a network device is reached, the terminal determines thata beam failure event occurs.

The terminal further needs to perform new candidate beam identification:The physical layer of the terminal measures a candidate beam RS andsearches for a new candidate beam. The step of searching for a newcandidate beam is not necessarily performed after occurrence of a beamfailure event is determined. The step can also be performed before thedetermining of a beam failure event. When the physical layer of theterminal receives a request, an instruction, or a notification from thehigher layer (e.g., the MAC layer) of the terminal, the physical layerof the terminal reports, to the higher layer of the terminal, ameasurement result that the preset condition (measurement quality of thecandidate beam RS exceeds a preset L1-RSRP threshold) is met, and thereport content is {beam RS index, L1-RSRP}. The higher layer of theterminal selects a candidate beam based on the reporting from thephysical layer.

In this embodiment of this disclosure, after occurrence of the beamfailure event is determined and the new candidate beam is found, andbefore the step of monitoring a PDCCH on a CORESET-BFR, the beam failurerecovery process further includes: sending a beam failure recoveryrequest to the network device.

Specifically, the higher layer (e.g., the MAC layer) of the terminaldetermines a Physical Random Access Channel (PRACH) resource/sequencebased on the selected candidate beam. If the terminal determines that atriggering condition of the beam failure recovery request is met, theterminal sends the beam failure recovery request to the network deviceon a non-contention-based PRACH. The terminal needs to send the beamfailure recovery request based on a quantity of times of sending thebeam failure recovery request and/or a timer configured by the networkdevice. A non-contention-based PRACH resource herein and other PRACHresources (such as a PRACH resource used for initial access) may beFrequency Division Multiplexing (FDM) or Code Division Multiplexing(CDM). PRACH preambles in CDM need to be designed with a same sequence.

In this embodiment of this disclosure, after sending the beam failurerecovery request to the network device, the terminal monitors responseinformation of the network device in response to the beam failurerecovery request (UE monitors a gNB response for beam failure recoveryrequest). After receiving the beam failure recovery request, the networkdevice sends a response in a dedicated PDCCH on a CORESET-BFR. The beamfailure recovery request carries a Cell Radio Network TemporaryIdentifier (C-RNTI) and may possibly further include an instruction forswitching to the new candidate beam, an instruction for restarting beamsearching, or another instruction. The CORESET-BFR and a DownlinkReference Signal (DL RS) of a candidate beam found by the terminal arespatial QCL. If beam failure recovery fails, the physical layer of theterminal sends an instruction to the higher layer of the terminal forthe higher layer to determine a subsequent radio link failure process.

That is, the step of monitoring a PDCCH on a CORESET-BFR includes:monitoring the response information in the PDCCH on the CORESET-BFR,where the response information is response information fed back by thenetwork device in response to the beam failure recovery request.

In this embodiment of this disclosure, the step of monitoring a PDCCH ona CORESET-BFR and a PDCCH on another CORESET includes:

monitoring response information in the PDCCH on the CORESET-BFR within amonitoring window configured by the network device; and

monitoring the PDCCH on the another CORESET within the monitoring windowand/or outside the monitoring window.

Specifically, after a specified period of time for sending the beamfailure recovery request elapses, the terminal monitors a gNB responsein a dedicated PDCCH on the CORESET-BFR within the monitoring windowconfigured by the network device, so as to determine whether beamfailure recovery is successful.

The another CORESET may be monitored within the monitoring window, maybe monitored outside the monitoring window, or may be monitoredconstantly.

The following describes in detail a method of determining a QCLparameter of a PDSCH in this embodiment of this disclosure.

In this embodiment of this disclosure, a different approach forreceiving a PDSCH may be determined based on a magnitude relationshipbetween a preset threshold and a time interval (also referred to as “ascheduling offset”) between a time of receiving the DCI and a time ofreceiving the PDSCH scheduled by the DCI is less than a presetthreshold.

(1) In a case that the time interval between the time of receiving theDCI and the time of receiving the PDSCH scheduled by the DCI is lessthan the preset threshold, a first approach is used to determine the QCLparameter of the PDSCH, where the first approach is one of the followingapproaches:

(11) determining that the QCL parameter of the PDSCH is the same as theQCL parameter of the PDCCH on the CORESET-BFR;

(12) determining that the QCL parameter of the PDSCH is the same as aQCL parameter of a PDCCH on a preset CORESET in the another CORESET;

(13) determining that the QCL parameter of the PDSCH is the same as aQCL parameter of a PDCCH on a preset CORESET in all CORESETs, where allthe CORESETs include the CORESET-BFR and the another CORESET;

(14) determining that the QCL parameter of the PDSCH is the same as theQCL parameter of the PDCCH on the CORESET that contains the DCIscheduling the PDSCH; or

(15) determining that the QCL parameter of the PDSCH is the same as aQCL parameter of a PDCCH on a preset CORESET of a CORESET that containsa plurality of pieces of DCI scheduling the PDSCH.

The foregoing preset CORESET is a CORESET with a smallest ID in one ormore CORESETs configured with a search space within a slot in which asearch space is configured for the terminal. Certainly, the foregoingpreset CORESET may alternatively be another preset CORESET or a CORESETwith a largest ID in the one or more CORESETs configured with a searchspace within the slot in which the search space is configured for theterminal.

In this embodiment of this disclosure, the step of using a firstapproach to determine the QCL parameter of the PDSCH when a timeinterval between a time of receiving the DCI and a time of receiving thePDSCH scheduled by the DCI is less than a preset threshold includes:

in a case that the DCI contains no TCI state information used toindicate a QCL parameter (for example, DCI format 1_0 is used toschedule the PDSCH, and the DCI format 1_0 contains no TCI stateinformation used to indicate a QCL parameter) and the time interval isless than the preset threshold, using the first approach to determinethe QCL parameter of the PDSCH;

in a case that the network device configures a preset parameter (forexample, TCI-PresentInDCI) for the terminal, where the preset parameteris used to indicate whether the DCI contains TCI state information, avalue of the preset parameter is valid (for example, Enabled), and thetime interval is less than the preset threshold, using the firstapproach to determine the QCL parameter of the PDSCH; or

in a case that the network device configures the preset parameter (forexample, TCI-PresentInDCI) for the terminal, a value of the presetparameter is invalid (for example, Disabled), and the time interval isless than the preset threshold, using the first approach to determinethe QCL parameter of the PDSCH.

The preset parameter is configured for the terminal by the networkdevice by using higher-layer signaling.

(2) In a case that the time interval between the time of receiving theDCI and the time of receiving the PDSCH scheduled by the DCI is greaterthan or equal to the preset threshold, a second approach is used todetermine the QCL parameter of the PDSCH, where the second approach isone of the following approaches:

(21) determining that the QCL parameter of the PDSCH is the same as theQCL parameter of the PDCCH on the CORESET-BFR;

(22) in a case that the network device configures a preset parameter(for example, TCI-PresentInDCI) for the terminal, where the presetparameter is used to indicate whether the DCI contains TCI stateinformation, and a value of the preset parameter is valid (for example,Enabled), determining that the QCL parameter of the PDSCH is the QCLparameter indicated by the TCI state information in the DCI schedulingthe PDSCH;

(23) in a case that the DCI contains no TCI state information used toindicate a QCL parameter (for example, DCI format 1_0 is used toschedule the PDSCH, and the DCI format 1_0 contains no TCI stateinformation used to indicate a QCL parameter), determining that the QCLparameter of the PDSCH is the same as the QCL parameter of the PDCCH onthe CORESET that contains the DCI scheduling the PDSCH; or

(24) in a case that the network device configures the preset parameter(for example, TCI-PresentInDCI) for the terminal and a value of thepreset parameter is invalid (for example, Disabled), determining thatthe QCL parameter of the PDSCH is the same as the QCL parameter of thePDCCH on the CORESET that contains the DCI scheduling the PDSCH.

The preset parameter is configured for the terminal by the networkdevice by using higher-layer signaling.

In this embodiment of this disclosure, optionally, after the step ofdetermining a QCL parameter of the PDSCH based on a QCL parameter of thePDCCH on the CORESET-BFR, a QCL parameter of the PDCCH on the anotherCORESET, a QCL parameter of a PDCCH on a CORESET that contains DCIscheduling the PDSCH, or a QCL parameter indicated by TCI stateinformation in the DCI scheduling the PDSCH, the method furtherincludes:

redetermining the QCL parameter of the PDSCH when receiving from thenetwork device a reconfiguration, activation, or indication for TCIstate information of PDCCHs in all CORESETs, where all the CORESETsinclude the CORESET-BFR and the another CORESET;

redetermining the QCL parameter of the PDSCH when receiving from thenetwork device a reconfiguration, activation, or indication for TCIstate information of the PDCCH on the CORESET-BFR;

redetermining the QCL parameter of the PDSCH when receiving from thenetwork device a reconfiguration, activation, or indication for TCIstate information of a PDCCH on any CORESET in all the CORESETs;

redetermining the QCL parameter of the PDSCH when receiving from thenetwork device a reconfiguration, activation, or indication for TCIstate information of a PDCCH on any CORESET in the another CORESET; or

redetermining the QCL parameter of the PDSCH when receiving from thenetwork device a reconfiguration, activation, or indication for TCIstate information of PDCCHs on all the other CORESETs.

Referring to FIG. 2, an embodiment of this disclosure further provides aterminal 200, including:

a monitoring module 201, configured to monitor a PDCCH on a CORESET-BFRand a PDCCH on another CORESET during beam failure recovery, where theCORESET-BFR and the another CORESET are configured for the terminal by anetwork device;

a determining module 202, configured to determine a QCL parameter of aPDSCH based on a QCL parameter of the PDCCH on the CORESET-BFR, a QCLparameter of the PDCCH on the another CORESET, a QCL parameter of aPDCCH on a CORESET that contains DCI scheduling the PDSCH, or a QCLparameter indicated by TCI state information in the DCI scheduling thePDSCH; and

a receiving module 203, configured to receive the PDSCH based on thedetermined QCL parameter.

In this embodiment of this disclosure, the QCL parameter of the PDSCHcan be determined during beam failure recovery, so that the PDSCH iscorrectly received.

Optionally, the receiving module is further configured to receiveconfiguration information, sent by the network device, of theCORESET-BFR and the another CORESET, where the configuration informationincludes TCI state information used to indicate the QCL parameter of thePDCCH on the CORESET-BFR and TCI state information used to indicate theQCL parameter of the PDCCH on the another CORESET.

Optionally, the QCL parameter of the PDCCH on the another CORESET andthe QCL parameter of the PDCCH on the CORESET-BFR are the same ordifferent.

Optionally, the terminal further includes:

a sending module, configured to send a beam failure recovery request tothe network device; and

the monitoring module, configured to monitor response information in thePDCCH on the CORESET-BFR, where the response information is responseinformation fed back by the network device in response to the beamfailure recovery request.

Optionally, the monitoring module is further configured to monitorresponse information in the PDCCH on the CORESET-BFR within a monitoringwindow configured by the network device and monitor the PDCCH on theanother CORESET within the monitoring window and/or outside themonitoring window.

Optionally, the determining module is configured to, when a timeinterval between a time of receiving the DCI and a time of receiving thePDSCH scheduled by the DCI is less than a preset threshold, use a firstapproach to determine the QCL parameter of the PDSCH, where the firstapproach is one of the following approaches:

determining that the QCL parameter of the PDSCH is the same as the QCLparameter of the PDCCH on the CORESET-BFR;

determining that the QCL parameter of the PDSCH is the same as a QCLparameter of a PDCCH on a preset CORESET in the another CORESET;

determining that the QCL parameter of the PDSCH is the same as a QCLparameter of a PDCCH on a preset CORESET in all CORESETs, where all theCORESETs include the CORESET-BFR and the another CORESET;

determining that the QCL parameter of the PDSCH is the same as the QCLparameter of the PDCCH on the CORESET that contains the DCI schedulingthe PDSCH; or

determining that the QCL parameter of the PDSCH is the same as a QCLparameter of a PDCCH on a preset CORESET of a CORESET that contains aplurality of pieces of DCI scheduling the PDSCH.

Optionally, the determining module is configured to use the firstapproach to determine the QCL parameter of the PDSCH in a case that theDCI contains no TCI state information used to indicate a QCL parameterand the time interval is less than the preset threshold; or use thefirst approach to determine the QCL parameter of the PDSCH in a casethat the network device configures a preset parameter for the terminal,where the preset parameter is used to indicate whether the DCI containsTCI state information, a value of the preset parameter is valid, and thetime interval is less than the preset threshold; or use the firstapproach to determine the QCL parameter of the PDSCH in a case that thenetwork device configures the preset parameter for the terminal, a valueof the preset parameter is invalid, and the time interval is less thanthe preset threshold.

Optionally, the preset CORESET is a CORESET with a smallest ID in one ormore CORESETs that are configured with a search space within a slot inwhich a search space is configured for the terminal.

Optionally, the determining module is configured to, in a case that thetime interval between the time of receiving the DCI and the time ofreceiving the PDSCH scheduled by the DCI is greater than or equal to thepreset threshold, use a second approach to determine the QCL parameterof the PDSCH, where the second approach is one of the followingapproaches:

determining that the QCL parameter of the PDSCH is the same as the QCLparameter of the PDCCH on the CORESET-BFR;

in a case that the network device configures a preset parameter for theterminal, where the preset parameter is used to indicate whether the DCIcontains TCI state information, and a value of the preset parameter isvalid, determining that the QCL parameter of the PDSCH is the QCLparameter indicated by the TCI state information in the DCI schedulingthe PDSCH;

in a case that the DCI contains no TCI state information used toindicate a QCL parameter, determining that the QCL parameter of thePDSCH is the same as the QCL parameter of the PDCCH on the CORESET thatcontains the DCI scheduling the PDSCH; or

in a case that the network device configures the preset parameter forthe terminal and a value of the preset parameter is invalid, determiningthat the QCL parameter of the PDSCH is the same as the QCL parameter ofthe PDCCH on the CORESET that contains the DCI scheduling the PDSCH.

Optionally, the terminal further includes:

a redetermining module, configured to redetermine the QCL parameter ofthe PDSCH when receiving from the network device a reconfiguration,activation, or indication for TCI state information of PDCCHs in allCORESETs, where all the CORESETs include the CORESET-BFR and the anotherCORESET; or redetermine the QCL parameter of the PDSCH when receivingfrom the network device a reconfiguration, activation, or indication forTCI state information of the PDCCH on the CORESET-BFR; or redeterminethe QCL parameter of the PDSCH when receiving from the network device areconfiguration, activation, or indication for TCI state information ofa PDCCH on any CORESET in all the CORESETs; or redetermine the QCLparameter of the PDSCH when receiving from the network device areconfiguration, activation, or indication for TCI state information ofa PDCCH on any CORESET in the another CORESET; or redetermine the QCLparameter of the PDSCH when receiving from the network device areconfiguration, activation, or indication for TCI state information ofPDCCHs on all the other CORESETs.

FIG. 3 is a schematic diagram of a hardware structure of a terminal thatimplements the embodiments of this disclosure. The terminal 300 includesbut is not limited to components such as a radio frequency unit 301, anetwork module 302, an audio output unit 303, an input unit 304, asensor 305, a display unit 306, a user input unit 307, an interface unit308, a memory 309, a processor 310, and a power supply 311. A personskilled in the art can understand that the structure of the terminalshown in FIG. 3 does not constitute a limitation on the terminal, andthe terminal may include more or fewer components than those shown inthe figure, or a combination of some components, or the componentsdisposed differently. In the embodiments of this disclosure, theterminal includes but is not limited to a mobile phone, a tabletcomputer, a laptop computer, a personal digital assistant, an in-vehicleterminal, a wearable device, or a pedometer.

The processor 310 is configured to, after occurrence of a beam failureevent is determined, monitor a PDCCH on a CORESET-BFR and a PDCCH onanother CORESET, where the CORESET-BFR and the another CORESET areconfigured for the terminal by a network device, and determine a QCLparameter of a PDSCH based on a QCL parameter of the PDCCH on theCORESET-BFR, a QCL parameter of the PDCCH on the another CORESET, a QCLparameter of a PDCCH on a CORESET that contains DCI scheduling thePDSCH, or a QCL parameter indicated by TCI state information in the DCIscheduling the PDSCH.

The radio frequency unit 301 is configured to receive the PDSCH based onthe determined QCL parameter.

In this embodiment of this disclosure, the QCL parameter of the PDSCHcan be determined during beam failure recovery, so that the PDSCH iscorrectly received.

It should be understood that in this embodiment of this disclosure, theradio frequency unit 301 may be configured to receive and send signalsduring an information receiving and sending process or a call process.Specifically, the radio frequency unit 301 receives downlink data from abase station, then delivers the downlink data to the processor 310 forprocessing, and sends uplink data to the base station. Generally, theradio frequency unit 301 includes but is not limited to an antenna, atleast one amplifier, a transceiver, a coupler, a low noise amplifier, aduplexer, and the like. In addition, the radio frequency unit 301 mayfurther communicate with a network and another device through a wirelesscommunications system.

The terminal provides wireless broadband internet access for the user byusing the network module 302 and helps the user to, for example, sendand receive an email, browse a webpage, or access streaming media.

The audio output unit 303 may convert audio data that is received by theradio frequency unit 301 or the network module 302 or that is stored inthe memory 309 into an audio signal and outputs the audio signal as asound. In addition, the audio output unit 303 may further provide audiooutput related to a specific function (such as a calling signal receivesound and a message receive sound) executed by the terminal 300. Theaudio output unit 303 includes a loudspeaker, a buzzer, a receiver, andthe like.

The input unit 304 is configured to receive an audio or video signal.The input unit 304 may include a Graphics Processing Unit (GPU) 3041 anda microphone 3042. The graphics processing unit 3041 processes imagedata in a static picture or video obtained by an image capturingapparatus (for example, a camera) in a video capturing mode or an imagecapturing mode. A processed image frame may be displayed on the displayunit 306. The image frame obtained after processing by the graphicsprocessing unit 3041 may be stored in the memory 309 (or another storagemedium) or sent by the radio frequency unit 301 or the network module302. The microphone 3042 may receive a sound and is capable ofprocessing the sound as audio data. The processed audio data may beconverted, in a phone service mode, into a format that can be sent bythe radio frequency 301 to a mobile communication base station.

The terminal 300 may further include at least one sensor 305 such as alight sensor, a motion sensor, and another sensor. Specifically, thelight sensor includes an ambient light sensor and a proximity sensor.The ambient light sensor may adjust luminance of a display panel 3061based on brightness of ambient light, and the proximity sensor may turnoff the display panel 3061 and/or backlighting when the terminal 300moves to an ear. As a type of motion sensor, an accelerometer sensor candetect a value of an acceleration in each direction (usually, there arethree axes), can detect a magnitude and a direction of gravity when theterminal is static, and may be configured to recognize a mobile terminalposture (for example, screen switching between a landscape mode and aportrait mode, a related game, and magnetometer posture calibration),implement a vibration recognition related function (such as a pedometerand knocking), and the like. The sensor 305 may further include afingerprint sensor, a pressure sensor, an iris sensor, a molecularsensor, a gyroscope, a barometer, a hygrometer, a thermometer, aninfrared sensor, or the like. Details are not described herein.

The display unit 306 is configured to display information input by theuser or information provided for the user. The display unit 306 mayinclude the display panel 3061. The display panel 3061 may be configuredin a form of a Liquid Crystal Display (LCD) or an Organic Light-EmittingDiode (OLED), or the like.

The user input unit 307 may be configured to receive input digit orcharacter information, and generate a key signal input related to a usersetting and function control of the terminal. Specifically, the userinput unit 307 may include a touch panel 3071 and other input devices3072. The touch panel 3071, also referred to as a touchscreen, maycapture a touch operation of a user on or near the touch panel 3071 (forexample, an operation performed by the user by using any appropriateobject or accessory such as a finger or a stylus on the touch panel 3071or near the touch panel 3071). The touch panel 3071 may include twoparts: a touch detection apparatus and a touch controller. The touchdetection apparatus detects a touch orientation of the user, detects asignal brought by the touch operation, and transfers the signal to thetouch controller. The touch controller receives touch information fromthe touch detection apparatus, converts the touch information intocontact coordinates, and transmits the contact coordinates to theprocessor 310, and receives and executes a command transmitted by theprocessor 310. In addition, the touch panel 3071 may be implemented invarious types, such as a resistive type, a capacitive type, an infraredtype, and a surface acoustic wave type. The user input unit 307 mayinclude other input devices 3072 in addition to the touch panel 3071.Specifically, the other input devices 3072 may include but are notlimited to a physical keyboard, a function key (such as a volume controlkey or a switch key), a trackball, a mouse, a joystick, or the like.Details are not described herein again.

Further, the touch panel 3071 may cover the display panel 3061. Afterdetecting a touch operation on or near the touch panel 3071, the touchpanel 3071 transfers the touch operation to the processor 310 todetermine a touch event type. Subsequently, the processor 310 providescorresponding visual output on the display panel 3061 based on the touchevent type. In FIG. 3, the touch panel 3071 and the display panel 3061are used as two separate components to implement input and outputfunctions of the terminal. However, in some embodiments, the touch panel3071 may be integrated with the display panel 3061 to implement theinput and output functions of the terminal. This is not specificallylimited herein.

The interface unit 308 is an interface for an external apparatus toconnect to the terminal 300. For example, the external apparatus mayinclude a wired or wireless headphone port, an external power (or abattery charger) port, a wired or wireless data port, a memory cardport, a port used to connect an apparatus with an identification module,an audio input/output (I/O) port, a video I/O port, an earphone port,and the like. The interface unit 308 may be configured to receive input(such as data information and electricity) from the external apparatusand transmits the received input to one or more elements in the terminal300 or may be configured to transmit data between the terminal 300 andthe external apparatus.

The memory 309 may be configured to store a software program and varioustypes of data. The memory 309 may mainly include a program storage areaand a data storage area. The program storage area may store an operatingsystem, an application program required for at least one function (suchas a sound playback function and an image playback function), and thelike. The data storage area may store data created based on use of themobile phone (such as audio data and a phone book), and the like. Inaddition, the memory 309 may include a high-speed random access memory,or may include a non-volatile memory, for example, at least one diskstorage device, a flash memory device, or another volatile solid-statestorage device.

The processor 310 is a control center of the terminal, connects variousparts of the entire terminal by using various interfaces or lines, andperforms various functions of the terminal and processes data by runningor executing software programs and/or modules stored in the memory 309and calling data stored in the memory 309, so as to perform overallmonitoring on the terminal. The processor 310 may include one or moreprocessing units. Optionally, an application processor and a modemprocessor may be integrated into the processor 310. The applicationprocessor mainly processes an operating system, a user interface, anapplication program, and the like. The modem processor mainly processeswireless communication. It can be understood that the modem processormay alternatively not be integrated into the processor 310.

The terminal 300 may further include the power supply 311 (for example,a battery) that supplies power to the components. Optionally, the powersupply 311 may be logically connected to the processor 310 by using apower supply management system. In this way, functions such asmanagement of charging, discharging, and power consumption areimplemented by using the power supply management system.

In addition, the terminal 300 includes some function modules that arenot shown. Details are not described herein again.

Optionally, an embodiment of this disclosure further provides aterminal, including a processor, a memory, and a program that is storedin the memory and capable of running on the processor. When the programis executed by the processor, procedures in the foregoing embodiments ofthe method for receiving a PDSCH are implemented and the same technicaleffect can be achieved. To avoid repetition, details are not describedherein again.

An embodiment of this disclosure further provides a computer-readablestorage medium. The computer-readable storage medium stores a computerprogram. When the computer program is executed by a processor,procedures in the foregoing embodiments of the method for receiving aPDSCH are implemented and the same technical effect can be achieved. Toavoid repetition, details are not described herein again. Thecomputer-readable storage medium is, for example, a Read-Only Memory,(ROM), a Random Access Memory (RAM), a magnetic disk, or an opticaldisc.

It should be noted that in this specification, the terms “include”,“comprise”, or any of their variants are intended to cover anon-exclusive inclusion, such that a process, a method, an article, oran apparatus that includes a list of elements not only includes thoseelements but also includes other elements that are not expressly listed,or further includes elements inherent to such process, method, article,or apparatus. In absence of more constraints, an element preceded by“includes a . . . ” does not preclude the existence of other identicalelements in the process, method, article, or apparatus that includes theelement.

Through the description of the foregoing embodiments, a person skilledin the art can clearly appreciate that the method of the foregoingembodiments may be implemented by software on a necessarygeneral-purpose hardware platform, and certainly may alternatively beimplemented by hardware. However, in many cases, the former is a morepreferred implementation. Based on such an understanding, the technicalsolutions of this disclosure essentially or the part contributing to theprior art may be embodied in a form of a software product. The computersoftware product is stored in a storage medium (such as a ROM/RAM,magnetic disk, or optical disc) and includes several instructions forinstructing a terminal (which may be a mobile phone, a computer, aserver, an air conditioner, or a network device) to perform the methodsdescribed in the embodiments of this disclosure.

The embodiments of this disclosure are described above with reference tothe accompanying drawings, but this disclosure is not limited to theforegoing implementations. The foregoing embodiments are onlyillustrative rather than restrictive. Inspired by this disclosure, aperson of ordinary skill in the art can still derive many variationswithout departing from the essence of this disclosure and the protectionscope of the claims. All these variations shall fall within theprotection of this disclosure.

What is claimed is:
 1. A method for receiving a Physical Downlink SharedChannel (PDSCH), applied to a terminal and comprising: after occurrenceof a beam failure event is determined, monitoring a Physical DownlinkControl Channel (PDCCH) on a Control Resource Set for Beam FailureRecovery (CORESET-BFR) and a PDCCH on another CORESET, wherein theCORESET-BFR and the another CORESET are configured for the terminal by anetwork device; and determining a Quasi-Colocation (QCL) parameter ofthe PDSCH based on a QCL parameter of the PDCCH on the CORESET-BFR, aQCL parameter of the PDCCH on the another CORESET, a QCL parameter of aPDCCH on a CORESET that contains Downlink Control Information (DCI)scheduling the PDSCH, or a QCL parameter indicated by TransmissionConfiguration Indication (TCI) state information in the DCI schedulingthe PDSCH, and receiving the PDSCH based on the determined QCLparameter.
 2. The method for receiving a PDSCH according to claim 1,before determining a QCL parameter of the PDSCH, further comprising:receiving configuration information, sent by the network device, of theCORESET-BFR and the another CORESET, wherein the configurationinformation comprises TCI state information used to indicate the QCLparameter of the PDCCH on the CORESET-BFR and TCI state information usedto indicate the QCL parameter of the PDCCH on the another CORESET. 3.The method for receiving a PDSCH according to claim 1, before monitoringa PDCCH on a CORESET-BFR, further comprising: sending a beam failurerecovery request to the network device; and wherein monitoring a PDCCHon a CORESET-BFR comprises: monitoring response information in the PDCCHon the CORESET-BFR, wherein the response information is responseinformation fed back by the network device in response to the beamfailure recovery request.
 4. The method for receiving a PDSCH accordingto claim 1, wherein monitoring a PDCCH on a CORESET-BFR and a PDCCH onanother CORESET comprises: monitoring response information in the PDCCHon the CORESET-BFR within a monitoring window configured by the networkdevice; and monitoring the PDCCH on the another CORESET within themonitoring window and/or outside the monitoring window.
 5. The methodfor receiving a PDSCH according to claim 1, wherein determining a QCLparameter of the PDSCH based on a QCL parameter of the PDCCH on theCORESET-BFR, a QCL parameter of the PDCCH on the another CORESET, a QCLparameter of a PDCCH on a CORESET that contains DCI scheduling thePDSCH, or a QCL parameter indicated by TCI state information in the DCIscheduling the PDSCH comprises: determining that the QCL parameter ofthe PDSCH is the same as the QCL parameter of the PDCCH on theCORESET-BFR.
 6. The method for receiving a PDSCH according to claim 1,wherein determining a QCL parameter of the PDSCH based on a QCLparameter of the PDCCH on the CORESET-BFR, a QCL parameter of the PDCCHon the another CORESET, a QCL parameter of a PDCCH on a CORESET thatcontains DCI scheduling the PDSCH, or a QCL parameter indicated by TCIstate information in the DCI scheduling the PDSCH comprises: when a timeinterval between a time of receiving the DCI and a time of receiving thePDSCH scheduled by the DCI is less than a preset threshold, using afirst approach to determine the QCL parameter of the PDSCH, wherein thefirst approach is one of the following approaches: determining that theQCL parameter of the PDSCH is the same as the QCL parameter of the PDCCHon the CORESET-BFR; determining that the QCL parameter of the PDSCH isthe same as a QCL parameter of a PDCCH on a preset CORESET in theanother CORESET; determining that the QCL parameter of the PDSCH is thesame as a QCL parameter of a PDCCH on a preset CORESET in all CORESETs,wherein all the CORESETs comprise the CORESET-BFR and the anotherCORESET; determining that the QCL parameter of the PDSCH is the same asthe QCL parameter of the PDCCH on the CORESET that contains the DCIscheduling the PDSCH; or determining that the QCL parameter of the PDSCHis the same as a QCL parameter of a PDCCH on a preset CORESET of aCORESET that contains a plurality of pieces of DCI scheduling the PDSCH.7. The method for receiving a PDSCH according to claim 6, wherein usinga first approach to determine the QCL parameter of the PDSCH when a timeinterval between a time of receiving the DCI and a time of receiving thePDSCH scheduled by the DCI is less than a preset threshold comprises: ina case that the DCI contains no TCI state information used to indicate aQCL parameter and the time interval is less than the preset threshold,using the first approach to determine the QCL parameter of the PDSCH; ina case that the network device configures a preset parameter for theterminal, wherein the preset parameter is used to indicate whether theDCI contains TCI state information, a value of the preset parameter isvalid, and the time interval is less than the preset threshold, usingthe first approach to determine the QCL parameter of the PDSCH; or in acase that the network device configures the preset parameter for theterminal, a value of the preset parameter is invalid, and the timeinterval is less than the preset threshold, using the first approach todetermine the QCL parameter of the PDSCH.
 8. The method for receiving aPDSCH according to claim 6, wherein the preset CORESET is a CORESET witha smallest ID in one or more CORESETs that are configured with a searchspace within a slot in which search space is configured for theterminal.
 9. The method for receiving a PDSCH according to claim 1,wherein determining a QCL parameter of the PDSCH based on a QCLparameter of the PDCCH on the CORESET-BFR, a QCL parameter of the PDCCHon the another CORESET, a QCL parameter of a PDCCH on a CORESET thatcontains DCI scheduling the PDSCH, or a QCL parameter indicated by TCIstate information in the DCI scheduling the PDSCH comprises: in a casethat a time interval between a time of receiving the DCI and a time ofreceiving the PDSCH scheduled by the DCI is greater than or equal to apreset threshold, using a second approach to determine the QCL parameterof the PDSCH, wherein the second approach is one of the followingapproaches: determining that the QCL parameter of the PDSCH is the sameas the QCL parameter of the PDCCH on the CORESET-BFR; in a case that thenetwork device configures a preset parameter for the terminal, whereinthe preset parameter is used to indicate whether the DCI contains TCIstate information, and a value of the preset parameter is valid,determining that the QCL parameter of the PDSCH is the QCL parameterindicated by the TCI state information in the DCI scheduling the PDSCH;in a case that the DCI contains no TCI state information used toindicate a QCL parameter, determining that the QCL parameter of thePDSCH is the same as the QCL parameter of the PDCCH on the CORESET thatcontains the DCI scheduling the PDSCH; or in a case that the networkdevice configures the preset parameter for the terminal and a value ofthe preset parameter is invalid, determining that the QCL parameter ofthe PDSCH is the same as the QCL parameter of the PDCCH on the CORESETthat contains the DCI scheduling the PDSCH.
 10. The method for receivinga PDSCH according to claim 1, after determining a QCL parameter of thePDSCH based on a QCL parameter of the PDCCH on the CORESET-BFR, a QCLparameter of the PDCCH on the another CORESET, a QCL parameter of aPDCCH on a CORESET that contains DCI scheduling the PDSCH, or a QCLparameter indicated by TCI state information in the DCI scheduling thePDSCH, further comprising: redetermining the QCL parameter of the PDSCHwhen receiving from the network device a reconfiguration, activation, orindication for TCI state information of PDCCHs in all CORESETs, whereinall the CORESETs comprise the CORESET-BFR and the another CORESET;redetermining the QCL parameter of the PDSCH when receiving from thenetwork device a reconfiguration, activation, or indication for TCIstate information of the PDCCH on the CORESET-BFR; redetermining the QCLparameter of the PDSCH when receiving from the network device areconfiguration, activation, or indication for TCI state information ofa PDCCH on any CORESET in all the CORESETs; redetermining the QCLparameter of the PDSCH when receiving from the network device areconfiguration, activation, or indication for TCI state information ofa PDCCH on any CORESET in the another CORESET; or redetermining the QCLparameter of the PDSCH when receiving from the network device areconfiguration, activation, or indication for TCI state information ofPDCCHs on all the other CORESETs.
 11. A terminal, comprising aprocessor, a memory, and a program stored in the memory and capable ofrunning on the processor, wherein the program, when executed by theprocessor, causes the processor to perform a method, for receiving aPDSCH, the method comprising: after occurrence of a beam failure eventis determined, monitoring a PDCCH on a CORESET-BFR and a PDCCH onanother CORESET, wherein the CORESET-BFR and the another CORESET areconfigured for the terminal by a network device; and determining a QCLparameter of the PDSCH based on a QCL parameter of the PDCCH on theCORESET-BFR, a QCL parameter of the PDCCH on the another CORESET, a QCLparameter of a PDCCH on a CORESET that contains DCI scheduling thePDSCH, or a QCL parameter indicated by TCI state information in the DCIscheduling the PDSCH, and receiving the PDSCH based on the determinedQCL parameter.
 12. The terminal according to claim 11, wherein, beforedetermining a QCL parameter of the PDSCH, the method further comprises:receiving configuration information, sent by the network device, of theCORESET-BFR and the another CORESET, wherein the configurationinformation comprises TCI state information used to indicate the QCLparameter of the PDCCH on the CORESET-BFR and TCI state information usedto indicate the QCL parameter of the PDCCH on the another CORESET. 13.The terminal according to claim 11, wherein, before monitoring a PDCCHon a CORESET-BFR, the method further comprises: sending a beam failurerecovery request to the network device; and wherein monitoring a PDCCHon a CORESET-BFR comprises: monitoring response information in the PDCCHon the CORESET-BFR, wherein the response information is responseinformation fed back by the network device in response to the beamfailure recovery request.
 14. The terminal according to claim 11,wherein monitoring a PDCCH on a CORESET-BFR and a PDCCH on anotherCORESET comprises: monitoring response information in the PDCCH on theCORESET-BFR within a monitoring window configured by the network device;and monitoring the PDCCH on the another CORESET within the monitoringwindow and/or outside the monitoring window.
 15. The terminal accordingto claim 11, wherein determining a QCL parameter of the PDSCH based on aQCL parameter of the PDCCH on the CORESET-BFR, a QCL parameter of thePDCCH on the another CORESET, a QCL parameter of a PDCCH on a CORESETthat contains DCI scheduling the PDSCH, or a QCL parameter indicated byTCI state information in the DCI scheduling the PDSCH comprises:determining that the QCL parameter of the PDSCH is the same as the QCLparameter of the PDCCH on the CORESET-BFR.
 16. The terminal according toclaim 11, wherein determining a QCL parameter of the PDSCH based on aQCL parameter of the PDCCH on the CORESET-BFR, a QCL parameter of thePDCCH on the another CORESET, a QCL parameter of a PDCCH on a CORESETthat contains DCI scheduling the PDSCH, or a QCL parameter indicated byTCI state information in the DCI scheduling the PDSCH comprises: when atime interval between a time of receiving the DCI and a time ofreceiving the PDSCH scheduled by the DCI is less than a presetthreshold, using a first approach to determine the QCL parameter of thePDSCH, wherein the first approach is one of the following approaches:determining that the QCL parameter of the PDSCH is the same as the QCLparameter of the PDCCH on the CORESET-BFR; determining that the QCLparameter of the PDSCH is the same as a QCL parameter of a PDCCH on apreset CORESET in the another CORESET; determining that the QCLparameter of the PDSCH is the same as a QCL parameter of a PDCCH on apreset CORESET in all CORESETs, wherein all the CORESETs comprise theCORESET-BFR and the another CORESET; determining that the QCL parameterof the PDSCH is the same as the QCL parameter of the PDCCH on theCORESET that contains the DCI scheduling the PDSCH; or determining thatthe QCL parameter of the PDSCH is the same as a QCL parameter of a PDCCHon a preset CORESET of a CORESET that contains a plurality of pieces ofDCI scheduling the PDSCH.
 17. The terminal according to claim 16,wherein using a first approach to determine the QCL parameter of thePDSCH when a time interval between a time of receiving the DCI and atime of receiving the PDSCH scheduled by the DCI is less than a presetthreshold comprises: in a case that the DCI contains no TCI stateinformation used to indicate a QCL parameter and the time interval isless than the preset threshold, using the first approach to determinethe QCL parameter of the PDSCH; in a case that the network deviceconfigures a preset parameter for the terminal, wherein the presetparameter is used to indicate whether the DCI contains TCI stateinformation, a value of the preset parameter is valid, and the timeinterval is less than the preset threshold, using the first approach todetermine the QCL parameter of the PDSCH; or in a case that the networkdevice configures the preset parameter for the terminal, a value of thepreset parameter is invalid, and the time interval is less than thepreset threshold, using the first approach to determine the QCLparameter of the PDSCH.
 18. The terminal according to claim 11, whereindetermining a QCL parameter of the PDSCH based on a QCL parameter of thePDCCH on the CORESET-BFR, a QCL parameter of the PDCCH on the anotherCORESET, a QCL parameter of a PDCCH on a CORESET that contains DCIscheduling the PDSCH, or a QCL parameter indicated by TCI stateinformation in the DCI scheduling the PDSCH comprises: in a case that atime interval between a time of receiving the DCI and a time ofreceiving the PDSCH scheduled by the DCI is greater than or equal to apreset threshold, using a second approach to determine the QCL parameterof the PDSCH, wherein the second approach is one of the followingapproaches: determining that the QCL parameter of the PDSCH is the sameas the QCL parameter of the PDCCH on the CORESET-BFR; in a case that thenetwork device configures a preset parameter for the terminal, whereinthe preset parameter is used to indicate whether the DCI contains TCIstate information, and a value of the preset parameter is valid,determining that the QCL parameter of the PDSCH is the QCL parameterindicated by the TCI state information in the DCI scheduling the PDSCH;in a case that the DCI contains no TCI state information used toindicate a QCL parameter, determining that the QCL parameter of thePDSCH is the same as the QCL parameter of the PDCCH on the CORESET thatcontains the DCI scheduling the PDSCH; or in a case that the networkdevice configures the preset parameter for the terminal and a value ofthe preset parameter is invalid, determining that the QCL parameter ofthe PDSCH is the same as the QCL parameter of the PDCCH on the CORESETthat contains the DCI scheduling the PDSCH.
 19. The terminal accordingto claim 11, wherein, after determining a QCL parameter of the PDSCHbased on a QCL parameter of the PDCCH on the CORESET-BFR, a QCLparameter of the PDCCH on the another CORESET, a QCL parameter of aPDCCH on a CORESET that contains DCI scheduling the PDSCH, or a QCLparameter indicated by TCI state information in the DCI scheduling thePDSCH, the method further comprises: redetermining the QCL parameter ofthe PDSCH when receiving from the network device a reconfiguration,activation, or indication for TCI state information of PDCCHs in allCORESETs, wherein all the CORESETs comprise the CORESET-BFR and theanother CORESET; redetermining the QCL parameter of the PDSCH whenreceiving from the network device a reconfiguration, activation, orindication for TCI state information of the PDCCH on the CORESET-BFR;redetermining the QCL parameter of the PDSCH when receiving from thenetwork device a reconfiguration, activation, or indication for TCIstate information of a PDCCH on any CORESET in all the CORESETs;redetermining the QCL parameter of the PDSCH when receiving from thenetwork device a reconfiguration, activation, or indication for TCIstate information of a PDCCH on any CORESET in the another CORESET; orredetermining the QCL parameter of the PDSCH when receiving from thenetwork device a reconfiguration, activation, or indication for TCIstate information of PDCCHs on all the other CORESETs.
 20. Acomputer-readable storage medium, the computer-readable storage mediumstoring a program, wherein the program, when executed by a processor,causes the processor to perform a method, for receiving a PDSCH, appliedto a terminal, the method comprising: after occurrence of a beam failureevent is determined, monitoring a PDCCH on a CORESET-BFR and a PDCCH onanother CORESET, wherein the CORESET-BFR and the another CORESET areconfigured for the terminal by a network device; and determining a QCLparameter of the PDSCH based on a QCL parameter of the PDCCH on theCORESET-BFR, a QCL parameter of the PDCCH on the another CORESET, a QCLparameter of a PDCCH on a CORESET that contains DCI scheduling thePDSCH, or a QCL parameter indicated by TCI state information in the DCIscheduling the PDSCH, and receiving the PDSCH based on the determinedQCL parameter.